#react todo app

[codylambertdanafoster]

to diagnose arthritis gastritis smoking immune symptoms skin generate a react component for a todo list app after brian hood

[aloneharper]

10 Lessons I Learned from a Principal Engineer That Made Me a Better Developer

Hard-won wisdom from someone years ahead on the path

Early in my software career, I was fortunate to work closely with a Principal Engineer — the kind of person who could look at spaghetti code, raise an eyebrow, and calmly rewrite it into something elegant in half the time. While I was trying to write clever code, they were quietly writing effective code.

Over a year of mentorship and code reviews, I picked up far more than just technical skills. These 10 lessons reshaped the way I think about development — and they might just do the same for you.

Write Code for the Next Developer, Not for the Compiler

“If you’re the only one who understands your code, it’s broken.”

Sure, the compiler doesn't care how your code looks. But humans do. The Principal Engineer always prioritized readability over cleverness. Simple, well-named functions and consistent formatting will save more bugs — and more teammates — than you think.

Premature Optimization Is the Root of Most Technical Debt

I once tried to optimize a module with micro-caching logic. His response: “Let’s first see if this is actually a bottleneck.” Turned out it wasn’t. We wasted hours.

Build it simple and correct first. Optimize only when necessary, and only with real data.

Deeply Understand the Abstractions You Rely On

“Using an ORM doesn’t mean you understand how SQL works.”

He constantly encouraged me to “pop the hood” — whether it was understanding how Promises actually resolve or how React reconciliation really works. It’s okay to use abstractions, but understanding their mechanics makes you a more confident and resilient developer.

A Good Developer Can Explain Anything to a Junior Developer

The Principal Engineer could break down complex architecture in plain English — no jargon, no ego. I learned that true mastery includes the ability to teach, not just code.

Every TODO Is a Debt You’re Accruing

Leaving a TODO or “fix later” in code was always met with a raised eyebrow.

“Later usually means never.”

If you can’t fix it now, document it thoroughly and attach a ticket. Otherwise, you’re just adding interest to future pain.

Test the Way Your Users Use It — Not Just What You Built

While I wrote happy-path tests, he wrote edge cases and abuse cases.

“Users won’t use your app the way you intend. They’ll use it the way they want.”

Testing is not just about coverage — it’s about perspective.

Master the Tools Around the Code

The Principal Engineer spent as much time in Git, Docker, and CI pipelines as they did in the codebase. Why? Because knowing how to debug a flaky deploy or optimize a slow build saved everyone time.

If you only know how to write code, you're missing half the job.

Code Reviews Are a Two-Way Street

He treated junior devs’ code reviews seriously — not just correcting them, but asking why they made certain choices. Sometimes they had good reasons.

“You review code, not people. And you learn from both sides.”

Avoid Magic, Even If It Looks Cool

He hated frameworks that "just work" without transparency.

“If something breaks, and you don’t know how it works, you’re stuck.”

Clear logic beats magical behavior every time — especially at scale.

Your Job Isn’t to Code — It’s to Solve Problems

This one hit hardest.

“The code is just a tool. The real goal is to solve business and user problems.”

This mindset shifted how I write features, talk to stakeholders, and estimate work. It made me a product-minded developer — not just a coder.

Final Thoughts

The best developers I know didn’t get there through brute force or clever tricks. They learned through deliberate practice, humility, and absorbing lessons from those who came before them. Working with a Principal Engineer was like skipping years of trial and error.

These 10 lessons weren’t just advice — they were behaviors modeled in every code review, every whiteboard session, every debugging war room.

Whether you're junior, mid-level, or senior, keep learning from those around you — and someday, pass the lessons forward.

[dcpwebdesigners-blog]

How to Make Money with Programming: 9 Proven Ways to Earn from Your Coding Skills – Infographic

Programming isn’t just a skill, it’s a passport to countless income opportunities. Whether you’re a beginner or a seasoned developer, there are many ways to turn your coding knowledge into a reliable stream of income. 

In this blog post infographic, we’ll explore nine effective ways to make money with programming, from starting a blog to developing games and selling online courses.

Download Infographic

1. Blogging

If you enjoy writing and have a passion for coding, blogging can be a fantastic way to earn money. Starting a programming blog allows you to share tutorials, code snippets, solutions to technical problems, or industry news. Over time, as your blog gains traffic, you can monetise it through:

Google AdSense

Affiliate Marketing (promote tools like GitHub Copilot, hosting providers, or IDEs)

Sponsored Posts

Email List Marketing

Choose a specific niche like Python automation, web development, or data science to attract a targeted audience. The more value you provide, the more loyal readers and passive income you can build.

2. Sell Books

Programmers who can write clearly and teach effectively often find success in self-publishing. Writing an eBook or paperback on a specific programming language, framework, or topic can generate steady income. You could publish:

Beginner guides (e.g. “Learn Python in 30 Days”)

Advanced problem-solving books

Interview preparation guides

You can sell books on platforms like Amazon Kindle Direct Publishing, Gumroad, or your own website. Add bonus material like source code or video content to increase value.

3. Web/App Development

One of the most straightforward and lucrative ways to make money with programming is by developing websites or mobile apps. Businesses everywhere need online presence and custom solutions. You can:

Build websites using WordPress, React, or Laravel

Develop mobile apps using Flutter or React Native

Offer eCommerce development (e.g. Shopify or WooCommerce)

You can sell your services to local businesses, startup founders, or online clients. Alternatively, create your own app or SaaS (Software as a service) and monetise it through subscriptions or ads.

4. YouTube Tutorials

YouTube is a powerful platform for programmers looking to build an audience and generate income. If you’re good at explaining concepts, start a programming channel with:

Coding tutorials (e.g. “Build a Todo App in JavaScript”)

Explainer videos (e.g. “What is an API?”)

Career advice and learning paths

You can earn money through YouTube ad revenue, channel memberships, sponsored videos, and affiliate links. Once your audience grows, you can also use your channel to promote your own products, like courses or software.

5. Freelancing

Freelancing offers flexibility and the ability to earn while working on a wide variety of projects. Platforms like:

Upwork

Freelancer

Fiverr

Toptal

…connect you with clients looking for developers. Whether it’s bug fixes, full-stack development, automation scripts, or WordPress setup, there’s always demand. To succeed, create a strong portfolio, offer competitive pricing, and deliver great results to gain repeat clients and referrals.

6. Games Development

If you’re passionate about gaming and have strong programming skills, consider game development. Platforms like Unity (C#) or Unreal Engine (C++) make it accessible to solo developers. You can:

Create indie games and publish them on Steam or itch.io

Build mobile games and monetise via ads or in-app purchases

Sell game assets, templates, or source code

Some developers also earn by creating tutorials, documentation, or toolkits that help other game developers.

7. Competitions

Coding competitions and hackathons are not just fun, they can be profitable too. Websites like:

HackerRank

Codeforces

TopCoder

Kaggle (for data science)

…often have prize money or sponsorship opportunities. Many companies also host hackathons and innovation challenges where winners receive cash, job offers, or equity. Even if you don’t win, competitions sharpen your skills and can improve your resume or portfolio.

8. Sell Software

Have a great idea for a tool that solves a problem? Package it as software and sell it! This could include:

SaaS tools (e.g. CRM for freelancers)

Developer tools (e.g. code snippet managers)

Desktop apps (e.g. productivity tools)

Browser extensions

You can monetise through one-time purchases, monthly subscriptions, or freemium models with paid upgrades. Promote your product through your blog, social media, or YouTube channel to build traction.

9. Sell Courses

Online learning is booming, and if you’re an expert in a topic, you can create and sell your own programming course. Platforms like:

Udemy

Teachable

Gumroad

Skillshare

…allow you to host and sell your courses to a global audience. Courses could focus on specific programming languages, frameworks, or skills like API development, data analysis, or building real-world apps.

High-quality video content, practical projects, and community support (e.g. Discord or Facebook group) will help you stand out and keep your students engaged.

Conclusion

Programming is one of the most versatile and valuable skills you can have in today’s economy. Whether you would like to work for yourself or build a side hustle, there are many ways to make money with coding, from sharing your knowledge through blogs or courses to building products and solutions for clients or the marketplace.

The key is to start with one path, stay consistent, and keep learning. As you grow in experience and confidence, you can diversify your income by combining multiple strategies. For example, many successful developers run blogs, YouTube channels, and sell software or courses all at once.

So pick your starting point, and begin turning your coding skills into real-world income!

[some-programming-pearls]

Must-Know React Todo App for Beginners! (FULL Tutorial Available) #learn...

[dhaliwalmanjit]

How to Build Todo App Using React Js | Web Development | Learn Coding

[codezup]

Build a Todo List App with React Native: Step-by-Step Guide

1. Introduction Welcome to this comprehensive guide on building a real-world Todo List application using React Native. This tutorial is designed to help developers of all levels gain hands-on experience with React Native by creating a functional and feature-rich Todo List app. Through this guide, you’ll learn essential concepts and best practices that are applicable to a wide range of React…

[react-js-state-1]

Build a Simple To-Do List App with React

In this blog post, we will walk you through creating a simple yet functional To-Do List App using React. This application will allow users to add tasks, mark them as complete, and delete them. Let’s get started!

Step 1: Set Up the Project

To begin, set up a new React project. If React is not installed on your system, open your terminal or command prompt and run the following command:

npx create-react-app todo-app

This will create a folder named todo-app containing the React project files. Navigate to this folder and start the development server:

cd todo-app

npm start

Once the server is running, you’ll see the default React page in your browser.

Step 2: Create the To-Do App Structure

Next, let’s build the structure of our To-Do List App. Create a new file named TodoApp.js in the src directory. This file will contain the main React component for our app. Here is the code for the component:

import React, { useState } from 'react';

import './TodoApp.css';

const TodoApp = () => {

    const [tasks, setTasks] = useState([]);

    const [task, setTask] = useState('');

    // Function to add a task

    const addTask = () => {

        if (task.trim()) {

            setTasks([...tasks, { text: task, completed: false }]);

            setTask('');

        }

    };

    // Function to delete a task

    const deleteTask = (index) => {

        setTasks(tasks.filter((_, i) => i !== index));

    };

    // Function to toggle task completion

    const toggleComplete = (index) => {

        setTasks(

            tasks.map((task, i) =>

                i === index ? { ...task, completed: !task.completed } : task

            )

        );

    };

    return (

        <div className="todo-app">

            <h1>To-Do List App</h1>

            <div className="input-section">

                <input

                    type="text"

                    value={task}

                    onChange={(e) => setTask(e.target.value)}

                    placeholder="Add a new task"

                />

                <button onClick={addTask}>Add Task</button>

            </div>

            <ul>

                {tasks.map((task, index) => (

                    <li key={index} className={task.completed ? 'completed' : ''}>

                        <span>{task.text}</span>

                        <button onClick={() => toggleComplete(index)}>

                            {task.completed ? 'Undo' : 'Complete'}

                        </button>

                        <button onClick={() => deleteTask(index)}>Delete</button>

                    </li>

                ))}

            </ul>

        </div>

    );

};

export default TodoApp;

For More Information

Please Visit Our Website :- https://cyberinfomines.com/blog-details/todo-list-app

[kaoarika]

Another one of my old fics has been uploaded into my AO3 :)

Audience: Teen and Up Language: Spanish Chapters: 5 Words: 18,304 Drama, Friendship, Time Travel, Near Future, What-if Scenario, a little sci-fi, Alternate Universe - Canon Divergence

(Well, the latter one is a technicality, due to the time I wrote this one... and... stuff about time travels and a possible future)

Todos hemos querido saber acerca de lo que vamos a hacer en el futuro, e inclusive el más escéptico acerca del 'destino' como Switch, crea un visor con las altas posibilidades de sentirlo y poder vivirlo. Lo que le da un poco de curiosidad a Himeko. ¿Qué pasará con ella en el futuro? ¿O su vida amorosa? Sólo hay que tener en mente algo: el futuro no está escrito. (Escrito en 2013)

FVCR is a story about the future, possible outcomes of the decisions we take at the moment, and time travel through simulation? that stops being a simulation at some point and its consequences. You got your happiness... but at what cost?

(Also, although it features a prominent fan-favorite ship, it's not much about them, but rather the Sket Dan trio friendship... much a lot as the Sket Dance manga actually was)

I don't like to play "favoritisms" when I write stuff, but it's been almost 12 years and I still find this one of my favorite fics that I have written, lol. I dunno if it was because of the tone I was getting used to (very fresh with what I was reading of the Sukedan manga, which was WAY behind its Weekly Shonen Jump serialization at the time... REALLY, we have it SO much easier these days with the Mangaplus/Shonen Jump app) and I wanted to do something that wasn't too off in tone of the series: let's go a little sci-fi, but also make it prone to failure. (Shinohara made a whole arc about body/soul swapping w/o much actual scientific logic, in the actual series, and no, I reject the much more recent thought that this series might be in the same canon as Witch Watch due to the crossover cameos from early 2023, tbh?)

Rereading it made me remember how much I loved this story and its plot, and how I feel like I understood the tone and voices of the characters at that time and I had fun writing a possible future version of the characters that go through some stuff, and how their present selves would react back to it, all through the magic/science of "time travel", lol.

I suppose that, since "this is one of my favorite children stories", it's the one that I decided to format and edit it a little (especially more for readibility purposes - I had to separate dialogues and make them a little clearer than before, and change some words because I thought my choices were clever, but, nah 😭). It's probably the one that isn't going to be 1:1 to its original ff.net version, but, trust me, it's for the better?

You know how, sometimes, you look at an old work and think "hmmm, I could totally rewrite it nowadays?", well... when I read many of my old fanfics (including the ones I don't publish online, lmao). I usually think about it, once or twice, lol. But FVCR? I am still satisfied with the final result... although I could add some more angst for more drama (or make some corny scenes look LESS corny, and more reasonable, I feel? Some of the dialogue, too!), or add some scenes to make clearer some subtleties around the situations I do describe in this story. But, I'm still happy with how it came out.

(I could totally write these author notes? revision in Spanish, but... hey... HEY...)

[sergey-tihon]

F# Weekly #39, 2024 - new FAKE, Oxpecker in TechEmpower, Gleam to F# and .NET Days 2024

Welcome to F# Weekly, A roundup of F# content from this past week: News Certificate Issues on macOS 15 (“Sequoia”) · Issue #324 · dotnet/announcements First impressions + Roast my first F# code : r/fsharp Getting started with testing and .NET Aspire – .NET Blog Creating a React TODO app in Visual Studio 2022 – Visual Studio Blog Organize Your Breakpoints like a pro – Visual Studio…

[antoniohostinger]

🔐 Aula 27: Redefinição de Senha com React e Golang - Implementação Completa! 🔐

E aí, galera! Tudo certo?

Acabei de soltar mais uma aula top no curso de desenvolvimento web, e dessa vez a gente vai mergulhar de cabeça na implementação da funcionalidade de redefinição de senha. Se você tá seguindo o curso e quer deixar seu app ainda mais seguro, essa aula é pra você!

🌟 O que a gente vai ver:

Criação do Componente Reset.tsx: Vamos construir um formulário onde o usuário pode redefinir a senha usando o token enviado por e-mail.

Integração com o Backend: Conectando o frontend em React com o backend em Golang, tudo usando o framework Fiber.

Testes com MailHog: Testando o envio de e-mails e a redefinição de senha de forma segura e prática.

📘 Confere a aula completa aqui: https://www.codigofluente.com.br/aula-27-implementacao-da-funcionalidade-redefinir-senha

E se você tá curtindo o curso, que tal dar aquela força? Pode me apoiar no Ko-fi e ajudar a manter o conteúdo sempre atualizado! ☕💥 Acessa aqui: https://ko-fi.com/codigofluente

Dica extra: A gente ainda vai ver como fazer o deploy de todo esse projeto usando Docker, Kubernetes e Terraform. Fica ligado que tem mais coisa boa vindo por aí!

Nos vemos na próxima, valeu demais! 😉

[react-js-course]

REACTJS STATE MANAGEMENT

Table of Contents

Introduction

Understanding State in ReactJS

Why State Management is Crucial

Types of State in ReactJS

Local State

Global State

Server State

URL State

Common State Management Libraries in ReactJS

Redux

Context API

MobX

Recoil

React Native State Management

Best Practices for State Management in ReactJS

Examples of State Management in ReactJS

Simple Counter App

Todo List App

Advanced State Management Techniques

Middleware in Redux

Using Hooks for State Management

Challenges and Limitations of State Management in ReactJS

Future Trends in State Management

Conclusion

1. Introduction

State management is a fundamental aspect of ReactJS, a popular JavaScript library used for building user interfaces. It ensures that your application behaves predictably and efficiently by managing the state of different components. This article provides a comprehensive overview of ReactJS state management, covering various types, libraries, best practices, and real-world examples.

2. Understanding State in ReactJS

In ReactJS, state refers to a JavaScript object that holds dynamic information about a component. This data can change over time, leading to re-rendering of the component to reflect the latest state. Proper state management is vital for maintaining consistency and performance in your application.

3. Why State Management is Crucial

State management is crucial because it helps in:

Maintaining a consistent user interface

Managing data flow between components

Optimizing performance by preventing unnecessary re-renders

Ensuring that components remain decoupled and manageable

4. Types of State in ReactJS

4.1 Local State

Local state is confined to a single component. It is managed using the useState hook in functional components or the this.state and this.setState in class components.

4.2 Global State

Global state is shared across multiple components. It is typically managed using state management libraries like Redux or Context API.

4.3 Server State

Server state refers to data fetched from an external server. It is managed using data-fetching libraries like Axios or SWR, and needs to be synchronized with the local state.

4.4 URL State

URL state is part of the URL query string or path. It is useful for maintaining navigation state and can be managed using React Router.

5. Common State Management Libraries in ReactJS

5.1 Redux

Redux is a widely used state management library that follows a strict unidirectional data flow. It involves three core concepts: actions, reducers, and the store.

5.2 Context API

The Context API is a built-in feature of React that allows you to share state across components without prop drilling. It is suitable for small to medium-sized applications.

5.3 MobX

MobX is a reactive state management library that simplifies the management of observable state. It is known for its simplicity and ease of use.

5.4 Recoil

Recoil is a state management library for React that provides a more flexible approach than Context API or Redux. It allows you to create shared state and derived state.

6. React Native State Management

State management in React Native follows the same principles as ReactJS, with additional considerations for mobile app performance. Libraries like Redux and Context API are commonly used, along with AsyncStorage for persisting state.

7. Best Practices for State Management in ReactJS

Use local state for simple, isolated components

Use global state management for shared data

Avoid excessive state nesting

Normalize state shape

Keep state minimal and relevant to UI

Use memoization and selectors to optimize performance

8. Examples of State Management in ReactJS

8.1 Simple Counter App

A simple counter app demonstrates basic local state management using the useState hook.

8.2 Todo List App

A todo list app illustrates more complex state management, involving local state for individual items and global state for the list.

9. Advanced State Management Techniques

9.1 Middleware in Redux

Middleware in Redux allows for handling side effects, such as asynchronous actions or logging. Popular middleware libraries include Redux Thunk and Redux Saga.

9.2 Using Hooks for State Management

React hooks like useReducer and useContext provide powerful tools for managing state and side effects in functional components.

10. Challenges and Limitations of State Management in ReactJS

Complexity in managing large applications

Performance issues with deep state trees

The learning curve for libraries like Redux

Boilerplate code in some state management patterns

11. Future Trends in State Management

Future trends in state management may include:

Improved integration with server-side rendering (SSR)

More declarative state management approaches

Enhanced tooling for debugging and performance optimization

Wider adoption of newer libraries like Recoil

12. Conclusion

Effective state management is essential for building robust and scalable ReactJS applications. By understanding the various types of state, leveraging appropriate libraries, and following best practices, developers can ensure their applications remain performant and maintainable.

[fahrni]

Project Tapestry

Craig Hockenberry • Iconfactory

This post will explain the technology behind Project Tapestry and how we tested it as a prototype. We’ll keep this discussion at a fairly basic level: if you’re a web or app developer, you’ll have no problems following along.

And if you think I’m going to describe RSS feeds now, think again! We’ve come up with something completely new.

I’m excitedly looking forward to seeing the final product and I hope they make their stretch goal of bringing it to the Mac. 🤞🏼 Please, go read about Project Tapestry, and if you’re so inclined please support their effort. I backed them early, it was a no brainer for me.

I really wanted to talk about the choice the Iconfactory made to create a highly extensible platform for plugins. It’s a darned great idea! And I love their choice of pushing network requests through Project Tapestry itself as a way to guarantee plugins can’t phish out user data or credentials to exploit later. 👍🏼

As I was reading the post I came across Craig’s mention of the app having a sendRequest method used by the JavaScript code to make network requests. This grabbed my attention and made me realize this is a way better version of a React Native application.

What I mean by that is, React Native is hosted inside a native iOS application framework and uses native iOS controls on its view controllers or its version of a view controller. The JavaScript code drives everything from networking to user interface (it uses UIKit internally) to render content for the user to interact with. This allows developers to write their app using straight web technologies and run it on iOS and Android.

The project I’m currently involved in is an existing eight year old iOS application built with a mix of UIKit and SwiftUI. On the flip side the Android app of the same age is built using Java and Kotlin with a mix of the original XML based UI and modern Jetpack Compose. They’ve both taken very similar and not unexpected paths.

Enter React Native

Something our client wanted to do is integrate React Native into the existing applications. This has been done before by Airbnb and more recently by Shopify. Each with very different outcomes.

So all of that to say, ours has been successful, in my opinion. We’ve been able to fully integrate React Native and carve out a little set of API’s in the native application we expose to the React Native developers to do work the native application is already doing for them for free. Part of which is all the networking calls.

In the Tapestry blog post Craig points out sendRequest. It’s the call they use to handle requests to the internet for the JavaScript plugin. In our application we’ve exposed a makeRequest call that handles doing any type of network request; GET, POST, PUT, PATCH, or DELETE, and returns a Promise to the caller. Hey, sounds like the Tapestry code! 😄

I have it on my todo list to learn JavaScript. It’s been there for years and years because I knew I’d need it at some point. I really need it now. I can’t see React Native projects going away for the WillowTree team. They’re a very popular way for our clients to get cross platform code and get an iOS and Android app out the door simultaneously without having to spend time, money, and effort on two completely separate code bases.

Over the course of our integration work I’ve done a smidge of TypeScript code to allow other TypeScript devs on the team to make calls into the APIs we’ve exposed in the native application.

It’s been fun and I see a place for JavaScript/TypeScript in my native development world.

As for what Iconfactory is doing, I think it’s a much better version of what React Native does. It gives them the best of both worlds. A beautiful, hand crafted, fully native UI, that gives JavaScript developers the ability to extend the app. That’s a lovely thing. ❤️

[programmingfields65]

Todo App in React | Programming Fields

Programming Fields offers the best Todo App React experience, helping you to stay organized and productive. Get the most out of your tasks with our easy-to-use, intuitive interface.

todo app react

[codylambertdanafoster]

to diagnose arthritis gastritis smoking immune symptoms skin generate a react component for a todo list app after

spanish verb conjgation

moniquer meanses papering you monieue meanses happy fubling moniyeh = heart him findeses